Pattern libs/shared/**/*: "Confirm that the code adheres to the following:

• Cross-application utility functions, types, and constants.
• TypeScript best practices to ensure type safety and reusability.
• Documentation and examples for library consumers."

Pattern libs/**/*: "Confirm that the code adheres to the following:

• Reusability of components and hooks across different NextJS apps.
• TypeScript usage for defining props and exporting types.
• Effective tree-shaking and bundling practices."

Pattern apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

Pattern apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

Pattern apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

Pattern apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

Pattern apps/**/*: "Confirm that the code adheres to the following:

• NextJS best practices, including file structure, API routes, and static generation methods.
• Efficient state management and server-side rendering techniques.
• Optimal use of TypeScript for component and utility type safety."

Let me verify the GraphQL schema alignment by checking the actual schema definitions and their usage.

Let me try different commands to verify the GraphQL schema.

GraphQL schema types are properly aligned with the codebase
Based on the search results, all the imported types (ContentLanguage, CustomPageUniqueIdentifier, GetNamespaceQuery, OrganizationPage, Query, QueryGetNamespaceArgs, QueryGetOrganizationPageArgs) are defined in the GraphQL schema and are consistently used throughout the codebase. The types are properly defined in libs/clients/cms/schema.graphql and are actively used in multiple files, including the file under review.

The following scripts were executed for the analysis:

Error: No shell scripts found

Script:

#!/bin/bash
# Search for GraphQL schema definitions
rg -t graphql "type (ContentLanguage|CustomPageUniqueIdentifier|GetNamespaceQuery|OrganizationPage|Query)" --multiline

# Search for GraphQL query definitions related to these types
rg -t graphql "(getNamespace|getOrganizationPage).*\{" --multiline -A 5

# Check if these types are used consistently across the codebase
rg "QueryGetNamespaceArgs|QueryGetOrganizationPageArgs" -t typescript

Length of output: 365

Script:

#!/bin/bash
# Search for schema files
fd "schema.(ts|js|graphql)"

# Search for GraphQL type definitions in any file
rg "type (ContentLanguage|CustomPageUniqueIdentifier|GetNamespaceQuery|OrganizationPage)"

# Look for query definitions
rg "(getNamespace|getOrganizationPage)\s*(\(.*\))?\s*\{"

# Check type usage
rg "QueryGetNamespaceArgs|QueryGetOrganizationPageArgs"

Length of output: 24548

Let me verify the route mapping correctness by checking the Next.js pages and related configurations.

Let me check the actual page implementations to verify if these routes are properly set up.

Let me check for any catch-all or dynamic routes that might handle these paths, as well as search for any related components.

Route mapping is correctly implemented
The paths in the directorateoflabourmypages entry are verified to be correct. The implementation is supported by:

• Matching page files exist: apps/web/pages/s/vinnumalastofnun/minar-sidur/index.ts and apps/web/pages/en/o/directorate-of-labour/my-pages/index.ts
• The paths are consistently used in the DirectorateOfLabour component (apps/web/screens/Organization/DirectorateOfLabour/MyPages.tsx)
• The route structure follows the established pattern for organization pages in both languages

The following scripts were executed for the analysis:

Error: No shell scripts found

Script:

#!/bin/bash
# Search for files and directories that might contain route configurations or pages
fd -t f "page|route" apps/web/pages
fd -t f "page|route" apps/web/routes

# Search for any references to these specific paths
rg "/s/vinnumalastofnun/minar-sidur|/en/o/directorate-of-labour/my-pages" -A 2 -B 2

# Check for any other occurrences of similar route patterns
rg "/s/vinnumalastofnun|/en/o/directorate-of-labour" -A 2 -B 2

# Look for any Next.js configuration files that might contain route definitions
fd "next.config" .

Length of output: 1827

Script:

#!/bin/bash
# Check for files related to directorate of labour pages
fd -t f "vinnumalastofnun|directorate.*labour" apps/web/pages

# Look for dynamic route handlers that might handle these paths
fd "\[\[\.\.\..*\]\]\.ts" apps/web/pages

# Check the Next.js config for any relevant route configurations
cat apps/web/next.config.js

Length of output: 5961

Script:

#!/bin/bash
# Check for dynamic routes in organization-related paths
fd -t f . "apps/web/pages/s" "apps/web/pages/en/o"

# Look for components or utilities that might handle these routes
rg -g "!*.test.*" -g "!*.spec.*" "vinnumalastofnun" apps/web
rg -g "!*.test.*" -g "!*.spec.*" "directorate.*labour" apps/web

Length of output: 3207